|
|
|
Add controls to editable areas in the custom control. You can set properties for these controls in the Properties view, just as you would set properties for any other controls that you add to XPages. You can also change the facet name of controls in editable areas if you are computing the value at ... |
|
|
|
A custom control is a collection of controls that are stored as a single object. Similar to the way a subform can be placed on more than one form, a custom control can be created once and added to multiple XPages. When you update a custom control, every XPage that uses that custom control ... |
|
|
|
Add user interface (UI) controls to the custom control. Then, you can select each UI control individually and set properties for it just as you would for a UI control inside an XPage. |
|
|
|
Create a new custom control to use in XPages. |
|
|
|
Add the custom control to an XPage. |
|
|
|
Set general properties for custom controls. You can add a description, and set options for displaying the custom control in the Controls palette. |
|
|
|
Set properties for the custom control as it relates to the XPage that contains it. You can set properties for its name and visibility status as well as for any additional properties that you defined when setting properties for the custom control design element. |
|
|
|
Define the editable areas that you want to include in the custom control. Editable areas are regions that users can modify when the custom control is placed on an XPage. All other regions that fall outside of editable areas are read-only and cannot be modified. |
|
|
|
Set properties for editable areas in the custom control. You can set properties for the name of the editable area as well as the facet name. You can also configure how and if the editable area is visible inside the custom control at run time. |
|
|
|
Organize custom controls in the Controls palette. You can put them in categories for easy access. |
|
|
|
Define your own properties for the custom control. You can specify default editors and values to use when setting properties for custom controls inside XPages. You can also write scripts that determine when properties are visible and considered valid inside XPages. |
|
|
|
Set properties for the custom control as an independent design element. Properties include options for configuring data sources, applying styles, specifying validation and visibility settings, and more. |
|
|
|
The Controls palette contains the UI controls and custom controls used for designing the layout of XPages and determining how data will be entered and stored in the database. You can drag and drop controls from the Controls palette onto XPages. |
|
|
|
A custom control is a collection of controls that can be added to multiple XPages. When you update a custom control, every XPage that uses the custom control is automatically updated. |
|
|
|
The custom control interface is similar to the XPages interface including an edit area, properties area, controls palette, and data palette. |
|
|
|
Custom controls can be used on XPages and other custom controls. |
|
|
|
The custom control auto-remove functionality will sometimes result in "'compositeData' not found" error pages. |
|
|
|
If you have done any XPage development at all you know the power of using custom controls in your XPage design. One issue though is if you are using many custom controls on an XPage it is difficult to tell where the XPage design elements start/end and the Custom Control elements start/end. ... |